Systems and methods for second tap e-receipt option for NFC-enabled payment vehicles

ABSTRACT

Systems and methods are disclosed for generating electronic receipts (e-receipts) at point-of-sale (POS) terminals associated with a merchant at a retail location. The systems and methods include a near field communication (NFC) reader and an NFC-enabled payment vehicle. A POS terminal processes a payment transaction after an initial interaction between the NFC reader and the NFC-enabled payment vehicle. An e-receipt is generated when a second interaction is detected between the NFC reader and the NFC-enabled payment vehicle.

TECHNICAL FIELD

The present disclosure relates generally to the field of paymenttransactions and, more particularly, to the generation of electronicreceipts at point of sale (POS) terminals.

BACKGROUND

Merchants and other store owners have point of sale (POS) terminals andPOS systems that accept check or payment card payments from consumersfor goods and services. Brick-and-mortar merchants, in particular,generate paper receipts when finalizing payment transactions forconsumers. Merchants consequently incur increased operating costs whenhaving to print paper receipts for every payment transaction.

SUMMARY

A computer-implemented method is disclosed for managing electronicpayment transactions at a merchant location. The method comprisesinitiating a check-out procedure for a consumer to complete a paymenttransaction at a point-of-sale (POS) terminal associated with amerchant; prompting the consumer to present a payment vehicle andinteract with the POS terminal for completing the payment transaction;receiving an indication that an NFC-enabled payment vehicle interactedwith the POS terminal; receiving customer data from the NFC-enabledpayment vehicle; processing the payment transaction with the receivedcustomer data; receiving an indication that the NFC-enabled paymentvehicle interacted a second time with the POS terminal; generating ane-receipt as a result of the second NFC interaction, the e-receiptcomprising customizable features including consumer incentive features,interactive coupons, and/or loyalty rewards for the consumer; andtransmitting the e-receipt to the NFC-enabled payment vehicle fordisplay on the NFC-enabled payment vehicle.

A system is disclosed for managing electronic payment transactions at amerchant location, the system comprising: a data storage device storinginstructions for managing electronic payment transactions at a merchantlocation; and a processor configured to execute the instructions toperform a method including the steps of: initiating a check-outprocedure for a consumer to complete a payment transaction at apoint-of-sale (POS) terminal associated with a merchant; prompting theconsumer to present a payment vehicle and interact with the POS terminalfor completing the payment transaction; receiving an indication that anNFC-enabled payment vehicle interacted with the POS terminal; receivingcustomer data from the NFC-enabled payment vehicle; processing thepayment transaction with the received customer data; receiving anindication that the NFC-enabled payment vehicle interacted a second timewith the POS terminal; generating an e-receipt as a result of the secondNFC interaction, the e-receipt comprising customizable featuresincluding consumer incentive features, interactive coupons, and/orloyalty rewards for the consumer; and transmitting the e-receipt to theNFC-enabled payment vehicle for display on the NFC-enabled paymentvehicle.

A non-transitory computer readable medium is disclosed for use on atleast one computer system containing computer-executable programminginstructions for managing electronic payment transactions at a merchantlocation, the method comprising: initiating a check-out procedure for aconsumer to complete a payment transaction at a point-of-sale (POS)terminal associated with a merchant; prompting the consumer to present apayment vehicle and interact with the POS terminal for completing thepayment transaction; receiving an indication that an NFC-enabled paymentvehicle interacted with the POS terminal; receiving customer data fromthe NFC-enabled payment vehicle; processing the payment transaction withthe received customer data; receiving an indication that the NFC-enabledpayment vehicle interacted a second time with the POS terminal;generating an e-receipt as a result of the second NFC interaction, thee-receipt comprising customizable features including consumer incentivefeatures, interactive coupons, and/or loyalty rewards for the consumer;and transmitting the e-receipt to the NFC-enabled payment vehicle fordisplay on the NFC-enabled payment vehicle.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the detailed embodiments, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate exemplary embodiments of thepresent disclosure and together with the description, serve to explainthe principles of the disclosure.

FIG. 1 depicts a merchant environment for processing consumer paymenttransactions, according to one or more embodiments.

FIG. 2A depicts an NFC-enabled payment vehicle interacting with an NFCdevice during a payment transaction, according to one or moreembodiments.

FIG. 2B depicts an illustrative display of an NFC-enabled paymentvehicle after a successful payment transaction, according to one or moreembodiments.

FIG. 3 is a flow chart of an example process of a payment transactioninitiated between an NFC device and an NFC-enabled payment vehicle,according to one or more embodiments.

FIG. 4A depicts an NFC-enabled payment vehicle interacting with an NFCdevice after prompting to “tap” again for an e-receipt, according to oneor more embodiments.

FIG. 4B depicts an illustrative display of an NFC-enabled paymentvehicle and an e-receipt, according to one or more embodiments.

FIG. 5 is a flow chart depicting an example process for prompting aconsumer to “tap” the NFC-enabled payment vehicle a second time forretrieval of an e-receipt, according to one or more embodiments.

FIG. 6A depicts an NFC-enabled payment vehicle with an illustrativedisplay of an e-receipt and customizable e-receipt features, accordingto one or more embodiments.

FIG. 6B depicts an NFC-enabled payment vehicle with an illustrativedisplay of a customer experience rating feature, according to one ormore embodiments.

FIG. 6C depicts an NFC-enabled payment vehicle with an illustrativedisplay of coupons generated for a consumer, according to one or moreembodiments.

FIG. 7 is a block diagram of an example computing environment, accordingto one or more embodiments.

DETAILED DESCRIPTION

Various non-limiting embodiments of the present disclosure will now bedescribed to provide an overall understanding of the principles of thestructure, function, and use of systems and methods disclosed hereinrelated to the generation of electronic receipts (e-receipts). One ormore examples of these non-limiting embodiments are illustrated in theselected examples disclosed and described in detail with reference madeto FIGS. 1 through 7 in the accompanying drawings. Those of ordinaryskill in the art will understand that systems, apparatuses, devices, andmethods specifically described herein and illustrated in theaccompanying drawings are non-limiting embodiments. The featuresillustrated or described in connection with one non-limiting embodimentmay be combined with the features of other non-limiting environments.Such modifications and variations are intended to be included within thescope of the present disclosure.

The systems, apparatuses, devices, and methods disclosed herein aredescribed in detail by way of examples and with reference to thefigures. The examples discussed herein are examples only and areprovided to assist in the explanation of the apparatuses, devices,systems, and methods described herein. None of the features orcomponents shown in the drawings or discussed below should be taken asmandatory for any specific implementation of any of these apparatuses,devices, systems or methods unless specifically designated as mandatory.For ease of reading and clarity, certain components, modules, or methodsmay be described solely in connection with a specific figure. In thisdisclosure, any identification of specific techniques, arrangements,etc. either are related to a specific example presented or are merely ageneral description of such a technique, arrangement, etc.Identifications of specific details or examples are not intended to be,and should not be, construed as mandatory or limiting unlessspecifically designated as such. Any failure to specifically describe acombination or sub-combination of components should not be understood asan indication that any combination or sub-combination is not possible.It will be appreciated that modifications to disclosed and describedexamples, arrangements, configurations, components, elements,apparatuses, devices, systems, methods, etc. can be made and may bedesired for a specific application. Also, for any methods described,regardless of whether the method is described in conjunction with a flowdiagram, it should be understood that unless otherwise specified orrequired by context, any explicit or implicit ordering of stepsperformed in the execution of a method does not imply that those stepsmust be performed in the order presented but instead may be performed ina different order or in parallel.

Reference throughout the specification to “various embodiments,” “someembodiments,” “one embodiment,” “some example embodiments,” “one exampleembodiment,” or “an embodiment” means that a particular feature,structure, or characteristic described in connection with any embodimentis included in at least one embodiment. Thus, appearances of the phrases“in various embodiments,” “in some embodiments,” “in one embodiment,”“some example embodiments,” “one example embodiment,” or “in anembodiment” in places throughout the specification are not necessarilyall referring to the same embodiment. Furthermore, the particularfeatures, structures, or characteristics may be combined in any suitablemanner in one or more embodiments.

Throughout this disclosure, references to components or modulesgenerally refer to items that logically can be grouped together toperform a function or group of related functions. Like referencenumerals are generally intended to refer to the same or similarcomponents. Components and modules can be implemented in software,hardware, or a combination of software and hardware. The term “software”is used expansively to include not only executable code, for examplemachine-executable or machine-interpretable instructions, but also datastructures, data stores and computing instructions stored in anysuitable electronic format, including firmware, and embedded software.The terms “information” and “data” are used expansively and includes awide variety of electronic information, including executable code;content such as text, video data, and audio data, among others; andvarious codes or flags. The terms “information,” “data,” and “content”are sometimes used interchangeably when permitted by context. It shouldbe noted that although for clarity and to aid in understanding someexamples discussed herein might describe specific features or functionsas part of a specific component or module, or as occurring at a specificlayer of a computing device (for example, a hardware layer, operatingsystem layer, or application layer), those features or functions may beimplemented as part of a different component or module or operated at adifferent layer of a communication protocol stack.

As described above, a merchant may incur increased operation costs whenhaving to print paper receipts for every purchase transaction. Thus, theembodiments of the present disclosure are directed to reducing operatingcosts for merchants by providing consumers with the option to receive anelectronic receipt (e-receipt) at the time of purchase. Furthermore,embodiments may provide for the customization of e-receipts forproviding incentive features to benefit both merchants and consumers.

For simplicity, the description that follows will be provided byreference to a “payment vehicle” or a “payment card,” which generallyrefers to any type of financial alternative to currency. As is to beclear to those skilled in the art, no aspect of the present disclosureis specifically limited to a specific type of payment vehicle or paymentcard. Therefore, it is intended that the following descriptionencompasses the use of the present disclosure with many other forms offinancial alternatives to currency, including credit cards, debit cards,smart cards, single-use cards, prepaid cards, electronic currency (suchas might be provided through a cellular telephone or personal digitalassistant), and the like. Payment vehicles or payment cards can betraditional plastic transaction cards, titanium-containing, or othermetal-containing, transaction cards, clear and/or translucenttransaction cards, foldable or otherwise unconventionally-sizedtransaction cards, radio-frequency enabled transaction cards, or othertypes of transaction cards, such as credit, charge, debit, prepaid orstored-value cards, electronic benefit transfer cards, or any other likefinancial transaction instrument.

Point-of-sale (“POS”) systems used by merchants generally acceptpayments from consumers in the form of cash, check, credit cards and soforth. POS systems can include one or more POS terminals and can includeback-office computing systems. POS systems and POS terminals can bespecialized computing devices configured to send and receive financialtransaction data, for example between a POS system and a POS terminal,or with a payment network provider such as an acquirer processor.Acquirer processors similarly can use specialized computing devicesconfigured to send, receive, and process financial transaction data.

FIG. 1 depicts a payments processing network generally comprising amerchant 110, acquirer processor 130, financial institution 140, andconsumer 102, all provided in communication with each other via apayment network 120. The components of the payments processing networkmay be connected by any combination of wired or wireless networks, forexample, PSTNs and/or the Internet. Acquirer processor 130 (e.g.,acquiring bank) is in partnership with payment network 120, such thatthe acquirer processor 130 may process payments through, and on behalfof, payment network 120. Payment network 120 may in turn have apartnership with financial institution 140 (e.g., issuing bank).Financial institution 140 may hold accounts for one or more of consumer102. Consumer 102 may have a payment vehicle 101 (e.g., credit card,debit card, stored value card, etc.) which may be affiliated withpayment network 120. Consumer 102 may be able to use their paymentvehicle 101 for purchases from merchant 110.

Acquirer processor 130 may be an entity that provides a variety ofelectronic payment processing services to merchant 110. For example,acquirer processor 130 may be an entity that receives paymentinformation from a transaction that occurs at a POS terminal 112 atmerchant 110. The payment information may be, for example, payment cardinformation encoded in the magnetic stripe or EMV chip of paymentvehicle 101 and a payment amount of a transaction being made by, forexample, consumer 102 with merchant 110 using the payment card accountassociated with payment vehicle 101. Acquirer processor 130 may processthe information, and may send the information to the consumer'srespective financial institution 140 via an appropriate payment network120 depending on the particulars of payment vehicle 101. Processing theinformation may include, for example, determining the identity ofpayment network 120 and financial institution 140 associated with theparticular payment vehicle 101.

Acquirer processor 130 may also receive information from payment network120 such as confirmation or rejection of an attempted transaction usingpayment vehicle 101 and may convey that information to the appropriatePOS terminal. Moreover, acquirer processor 130 may provide securityand/or encryption services to merchant 110 and payment network 120; suchthat payments processed at POS terminal 112 may be completed with adecreased risk of data or financial theft or loss. Acquirer processor130 may be located, for example, remotely from merchant 110 that use itsservices, and may, for example, interact with merchant 110 primarilyover an electronic network, such as a data network or the Internet.

Payment network 120 may be, for example, a network that relays debitand/or credit transactions to and from various accounts at financialinstitution 140. For example, payment network 120 may have a partnershipprogram with financial institution 140 through which financialinstitution 140 may provide a payment vehicle account to consumer 102associated with payment network 120. Payment network 120 may also bepartnered with acquirer processor 130 which may manage paymenttransactions associated with payment network 120. Examples of paymentnetwork brands include, e.g., Visa, MasterCard, Discover, and AmericanExpress. While a single payment network 120 is illustrated, it is to beappreciated that multiple payment networks may be partnered with asingle or multiple acquirer processors.

Financial institution 140 may be a bank that manages payment accountsassociated with one or more of payment network 120 on behalf of one ormore of consumer 102. For example, financial institution 140 may allowfor consumer 102 to build up a revolving credit balance at financialinstitution 140 and may periodically receive payments from consumer 102to pay down the balance. Consumer 102 may be an individual, a company,or other entity having accounts with one or more of financialinstitution 140. Each consumer 102 may generally have at least onepayment vehicle 101 associated with each payment account held by thatconsumer. Each consumer 102 may have multiple accounts with multiplefinancial institutions 140 which may be affiliated with the same ordifferent payment network 120.

Merchant 110 may be a merchant offering goods and/or services for saleto consumer 102 who have contracted with acquirer processor 130.Merchant 110 may be equipped with POS terminal 112, which is configuredto receive payment information from payment vehicle 101 and to relayreceived payment information to acquirer processor 130. Merchant 110 canbe any type of merchant, such as a brick-and-mortar retail location oran e-commerce/web-based merchant with a POS terminal 112.

New payment modalities for purchasing goods and services enable consumer102 to pay using forms of payment other than cash, check, or paymentcard. For example, online vendors accept payments via third-partypayment providers, but can be termed third-party payment processors.Example third-party payment providers include, but are not limited toApplePay™, Android Pay™, PayPal™, and Samsung Pay™ among other suitablethird-party payment providers. Consumers 102 can pay for goods andservices using their mobile computing device, such as an iPhone™ fromApple™, or an Android™ based smartphone. These new payment types can bebeneficial to consumer 102 and merchant 110 alike. Consumer 102 canbenefit from the convenience of using mobile payment systems. Merchant110 can benefit from more economical transaction costs offered bythird-party payment providers. Many third-party payment providers usedigital wallets. Digital wallets provide flexibility to consumer 102,allowing consumer 102 to choose their preferred form of payment from oneor more accounts configured in their digital wallet. For example, forany transaction, consumer 102 can choose whether to pay from a paymentcard, bank account, or line of credit in their digital wallet. Digitalwallets also provide security to consumer 102 because the consumer'spayment card and bank account numbers are not provided to a merchant 110during checkout.

In FIG. 1, consumer 102 is shown to be associated with a payment vehicle101. As is to be appreciated, payment vehicle 101 can include any typeof payment vehicle that can be utilized to initiate a paymenttransaction. Unless otherwise specified herein, “payment vehicle”includes a virtual card, such as a display or screenshot for a mobilephone or for another portable device (e.g., a flash drive, smart chip, alaptop or portable computer), or for a computer device (e.g., a desktopcomputer) in combination with data indicative of an account number orother account indicative information. Data associated with the cards mayinclude an encrypted or unencrypted account number or other encrypted orunencrypted account indicative information and/or encrypted orunencrypted information associated with a particular card, issuer,creator, or group of merchants. It is also contemplated that the cardmay have multiple embodiments or forms. For example, the card may be aphysical card (e.g., in the form of magnetic striped plastic card), avirtual card (e.g., in the form of a display on a smart phone), or both.In embodiments in which the card is a virtual card, the correspondingaccount information (e.g., account number) would initially be providedto the consumer and the consumer would communicate the accountinformation to the merchant. The virtual card may be communicated bydisplaying a display or screenshot, and/or by transmitting a signal,such as by using a near field communication (NFC) technology, or othersecure transport technologies to complete the transaction with theselected merchant. NFC is a short range, high frequency, wirelesscommunication technology that enables the exchange of data betweendevices over a relatively short distance. Optionally, the virtual cardmay have a display element (e.g., a barcode or string of numbers) whichidentifies the account number associated with the card. Alternatively,the virtual card may have display elements relating to the merchantswhich accept the card. Thus, whether the card is physical or virtual, itcommunicates account information.

A POS terminal 112 of merchant 110 provides transaction information tothe payment network 120 using conventional payment transactioncommunications. When consumer 102 checks-out, or pays for the goods orservices, the identifying indicia of consumer 102 can be used forauthentication. In one configuration, the POS terminal 112 can includean NFC system 114. NFC system 114 can communicate wirelessly withpayment vehicle 101 of consumer 102, for example to obtain anauthorization code or identifying information of consumer 102 or ofpayment vehicle 101. In another configuration, POS terminal 112 caninclude a keypad 116. Consumer 102 can enter a personal identificationnumber on keypad 116 for making a payment. Other numbers or alphanumericcharacters, such as temporary passwords or authorization codes, are alsocontemplated as would be understood by one of ordinary skill in the art.In another configuration, POS terminal 112 can include a scanner 118.Consumer 102 can display a code, such as a barcode or quick response(QR) code on the display of their mobile computing device to provideidentifying indicia of consumer 102. Scanner 118 can be a handheldscanner, an embedded scanner such as is used to scan items at grocerystores, a camera, and so forth as would be understood by one of ordinaryskill in the art.

POS terminal 112 can include a display area 122. In various embodimentsthe display area 122 can be a window, a widget, or a pop-up, a webpage,and so forth, and be rectangular or nonrectangular, and occupy one ormultiple contiguous or non-contiguous areas of POS terminal 112.

POS terminal 112 can generate a payment request for payment by merchant110. The payment request can include information such as informationidentifying the merchant to acquirer processor 130 or the party ofpayment network 120, the payment amount, which can include a gratuity,identifying indicia for consumer 102, authentication information such aswhether the consumer was authenticated by merchant 110 using images ofconsumer 102, and/or authentication information such as personalidentification number entered on keypad 116 by the consumer, a codescanned by scanner 118, or information about consumer 102 or paymentvehicle received via NFC handshake or any other suitable authenticationinformation.

The payment request can be packaged into a data structure and sent tothe acquirer processor 130 or other transaction processing entity in thepayment network 120 for processing. Suitable data structures caninclude, but are not limited to, proprietary data structures, or datastructures to find a suitable notation such as Abstract Syntax NotationOne (ASN.1) or Java Script Object Notation (JSON), or any other suitableencoding formats or data structure as would be understood by one ofordinary skill in the art. In various embodiments, a mobile walletservice can be used or a third party payment provider's digital walletcan be accessed. Consumer 102 can configure the digital wallet to usethe desired bank account, payment card, or line of credit to be used inprocessing the transaction. Acquirer processor 130 can process thetransaction with financial institution 140, and POS terminal 112 canreceive confirmation of a successful transaction from payment network120. If not successful, POS terminal 112 can receive informationindicating why payment was not able to be made through financialinstitution 140. The transaction result can be displayed to consumer 102via any suitable method, including via display area 122 of POS terminal112.

FIGS. 2A-2B illustrate embodiments of an example system and method forfacilitating a check-out procedure. FIG. 2A depicts an interactionbetween an NFC-enabled payment vehicle 220 and an NFC device 210 forfacilitating a payment transaction during a check-out procedure. In someembodiments, NFC device 210 includes a display 212 for displaying orprompting messages to consumer 102. During a check-out procedure, theconsumer is prompted to “tap” the NFC-enabled payment vehicle 220 forinitiating a payment transaction. The term “tap” can be any kind ofmotion (e.g., waving or holding in close proximity) in which the NFCdevice 210 registers interaction (e.g., handshake) with the NFC-enabledpayment vehicle 220. After initiating the payment transaction, thepayments environment 100 processes whether the payment transaction issuccessful.

FIG. 2B depicts an illustrative display of an NFC-enabled paymentvehicle 220 after a successful purchase transaction. In someembodiments, the consumer's NFC-enabled payment vehicle 220 includes aplurality of indicators and selection areas for consumer 102. Forexample, indicator 240 communicates to consumer 102 the result of thepayment transaction. Indicator 250 prompts consumer 102 to “tap” theNFC-enabled payment vehicle 220 a second time to retrieve an electronicreceipt (e.g., e-receipt). While indicator 240 illustrates a successfulpayment transaction, it is to be appreciated that consumer 102 can beprompted to receive an electronic receipt even if a transaction isdeclined. Selection area 260 enables consumer 102 to customize otherfeatures or options to be displayed when an e-receipt is generated. Thecustomizable features will be described later with reference to FIGS.6A-6B.

FIG. 3 is a flow chart depicting an example process 300 for prompting aconsumer to “tap” the NFC-enabled payment vehicle to initiate a paymenttransaction. In step 310, consumer 102 is prompted to “tap” theNFC-enabled payment vehicle 220 to interact with NFC device 210. In someembodiments, the prompting message can be communicated to consumer 102via display area 122 of POS terminal 112. In other embodiments, theprompting message can be communicated via display 212 of NFC device 210.In step 320, the POS terminal 112 receives indication that theNFC-enabled payment vehicle 220 interacted with the NFC device. In step330, POS terminal 112 processes the payment transaction by receivingconsumer payment data from the NFC-enabled payment vehicle 220 andsending the consumer payment data to payment network 120. Paymentnetwork 120 can generally process payment transactions either online oroffline. In some embodiments, offline approvals may be processed at POSterminal 112 before sending the transaction information to paymentnetwork 120 (e.g., delayed processing). In other embodiments, an offlinetransaction may be processed at POS terminal 112 and declined withoutsending the transaction information to payment network 120. In step 340,POS terminal 112 receives the result of the payment transaction anddisplays the result. The result of the payment transaction can bedisplayed on display area 122 of POS terminal 112, display 212 of NFCdevice 210, and/or on indicator 240 of the NFC-enabled payment vehicle220.

FIGS. 4A-4B illustrate embodiments of an example system and method forfacilitating the generation of an e-receipt. FIG. 4A depicts a secondinteraction between the NFC-enabled payment vehicle 220 and NFC reader210 during the check-out process. After payments environment 100processes the payment transaction, consumer 102 is given the option toreceive an e-receipt. Consumers are given the option to receive ane-receipt whether the purchase transaction is approved or declined.Consumer 102 is prompted to “tap” the NFC-enabled payment vehicle 220 asecond time during the check-out process to retrieve an e-receipt.Indicator 250 in FIG. 2B provides an illustrative example of a prompt to“tap” again for an e-receipt. The prompt to “tap” again for an e-receiptcan alternatively be displayed on display 212 of NFC reader 210, or ondisplay area 122 of POS terminal 112.

FIG. 4B depicts an NFC-enabled payment vehicle 220 and an illustrativedisplay of an e-receipt 420. E-receipt 420 is generated as a result ofthe second “tap” and is displayed on the NFC-enabled payment vehicle220. In some embodiments, e-receipt 420 is displayed along with othercustomizable e-receipt features. Consumer 102 can customize additionale-receipt features by invoking selection area 260, as shown in FIG. 2B.While not illustrated in FIG. 4B, it can be appreciated that selectionarea 260 can also be configured to display along with e-receipt 420.

When invoking selection area 260, consumer 102 can enable or disable(not illustrated) any number of features to display when generatinge-receipt 420. Selection areas 430 and 440 are non-limiting examples ofcustomizable e-receipt features. Selection area 430, for instance, canbe a ranking feature inviting consumer 102 to rate their customerexperience at the time of the payment transaction. Selection area 440can be an incentive feature that generates coupons or other loyaltyrewards for the consumer. The customizable e-receipt options will befurther described later with reference to FIGS. 6A-6B.

FIG. 5 is a flow chart depicting an example process 500 for retrievingan e-receipt when finalizing a payment transaction. In step 505,consumer 102 is prompted to “tap” the NFC-enabled payment vehicle 220 asecond time to receive an e-receipt. In some embodiments, the prompt to“tap” again is communicated via indicator 250 of the NFC-enabled paymentvehicle 220, as shown in FIG. 2B. In other embodiments, the prompt to“tap” again is communicated via display area 122 of POS terminal 112 orvia display 212 of NFC device 210. In step 510, POS terminal 112determines whether NFC-enabled payment vehicle 220 interacts a secondtime with NFC device 210. If POS terminal 112 receives indication thatthe consumer “tapped” NFC-enabled payment vehicle 220 a second time,then the process proceeds to step 520. In step 520, an e-receipt 420 isgenerated and transferred to NFC-enabled payment vehicle 220. In someembodiments, e-receipt 420 is stored in a mobile wallet of NFC-enabledpayment vehicle 220. In step 530, e-receipt 420 is displayed on theNFC-enabled payment vehicle 220 and the checkout process is finalized.At step 510, if POS terminal 112 does not receive indication that theconsumer “tapped” the NFC-enabled payment vehicle 220 a second time,then the process proceeds to step 540. In step 540, the check-outprocess is finalized and the payment transaction is complete.

FIGS. 6A-6B illustrate examples of customizable e-receipt features todisplay when generating an e-receipt during a check-out process. FIG. 6Adepicts e-receipt 420 displayed along with customizable e-receiptfeatures. Selection areas 430 and 440 are non-limiting examples ofcustomizable features that can be generated to display along withe-receipt 420. Selection area 430, for instance, can be a rankingfeature inviting consumer 102 to rate their customer experience at thetime of purchase. Merchant 110 can incentivize consumer 102 to ratetheir customer experience in exchange for loyalty rewards (e.g.,credits, discounts, points, etc.).

FIG. 6B is an illustrative example of consumer 102 rating their customerexperience at the time of purchase. Indicator 615 displays the ratingchosen by the consumer 102. Feedback field 625 provides an area forconsumer 102 to input additional feedback for clarifying the consumer'sexperience. Submit field 630 can display an incentive feature, such as aloyalty reward (e.g., credits, discounts, points, etc.), for consumer102 in exchange for submitting the rating and/or the customer experiencefeedback.

FIG. 6C depicts an illustrative display of coupons 640 that consumer 102can redeem in future payment transactions. Coupons 640 are generatedwhen invoking selection area 440. In some embodiments, coupons 640 canbe generic and independent of the consumer's purchasing behavior. Inother embodiments, coupons 640 can be tailored to reward the consumer'spurchasing behavior and/or tailored to incentivize future purchasingbehavior.

The systems and processes described above can be performed on or betweenone or more computing devices. FIG. 7 illustrates an example computingdevice. A computing device 700 can be a server, a computing device thatis integrated with other systems or subsystems, a mobile computingdevice such as a smart phone, a cloud-based computing ability, and soforth. The computing device 700 can be any suitable computing device aswould be understood in the art, including without limitation, a customchip, and embedded processing device, a tablet computing device, a POSterminal 112 associated with the merchant 110, a back-office system of amerchant 110, a personal data assistant (PDA), a desktop, laptop,microcomputer, and minicomputer, a server, a mainframe, or any othersuitable programmable device. In various embodiments disclosed herein, asingle component can be replaced by multiple components and multiplecomponents can be replaced by single component to perform a givenfunction or functions. Except where such substitution would not beoperative, such substitution is within the intended scope of theembodiments.

The computing device 700 includes a processor 702 that can be anysuitable type of processing unit, for example a general-purpose centralprocessing unit (CPU), a reduced instruction set computer (RISC), aprocessor that has a pipeline or multiple processing capabilityincluding having multiple cores, a complex instruction set computer(CISC), a digital signal processor (DSP), application specificintegrated circuits (ASIC), a programmable logic devices (PLD), and afield programmable gate array (FPGA), among others. The computingresources can also include distributed computing devices, cloudcomputing resources, and virtual computing resources in general.

The computing device 700 also includes one or more memories 706, forexample read-only memory (ROM), random access memory (RAM), cache memoryassociated with the processor 702, or other memory such as dynamic RAM(DRAM), static RAM (SRAM), programmable ROM (PROM), electricallyerasable PROM (EEPROM), flash memory, a removable memory card or disc, asolid-state drive, and so forth. The computing device 700 also includesstorage media such as a storage device that can be configured to havemultiple modules, such as magnetic disk drives, floppy drives, tapedrives, hard drives, optical drives and media, magneto-optical drivesand media, compact disk drives, Compact Disc Read Only Memory (CD-ROM),compact disc recordable (CD-R), Compact Disk Rewritable (CD-RW), asuitable type of Digital Versatile Disc (DVD) or BluRay disc, and soforth. Storage media such as flash drives, solid-state hard drives,redundant array of individual discs (RAID), virtual drives, networkeddrives and other memory means including storage media on the processor702, or memories 706 are also contemplated as storage devices. It can beappreciated that such memory can be internal or external with respect tooperation of the disclosed embodiments. It can be appreciated thatcertain portions of the processes described herein can be performedusing instructions stored on a computer readable medium or media thatdirect computer system to perform the process steps. Non-transitorycomputable-readable media, as used herein, comprises allcomputer-readable media except for transitory, propagating signals.

Networking communication interfaces 708 can be configured to transmitto, or receive data from, other computing devices 700 across a network712. The network and communication interfaces 708 can be an Ethernetinterface, a radio interface, a Universal Serial Bus (USB) interface, orany other suitable communications interface and can include receivers,transmitter, and transceivers. For purposes of clarity, a transceivercan be referred to as a receiver or a transmitter when referring to onlythe input or only the output functionality of the transceiver. Examplecommunication interfaces 708 can include wire data transmission linkssuch as Ethernet and TCP/IP. The communication interfaces 708 caninclude wireless protocols for interfacing with private or publicnetworks 712. For example, the network and communication interfaces 708and protocols can include interfaces for communicating with privatewireless networks such as Wi-Fi network, one of the IEEE 802.11x familyof networks, or another suitable wireless network. The network andcommunication interfaces 708 can include interfaces and protocols forcommunicating with public wireless networks 708, using for examplewireless protocols used by cellular network providers, including CodeDivision Multiple Access (CDMA) and Global System for MobileCommunications (GSM). A computing device 700 can use network andcommunication interfaces 708 to communicate with hardware modules suchas a database or data store, or one or more servers or other networkedcomputing resources. Data can be encrypted or protected fromunauthorized access.

In various configurations, the computing device 700 can include a systembus 710 for interconnecting the various components of the computingdevice 700, or the computing device 700 can be integrated into one ormore chips such as programmable logic device or application specificintegrated circuit (ASIC). The system bus 710 can include a memorycontroller, a local bus, or a peripheral bus for supporting input andoutput devices 704, and communication interfaces 708. Example input andoutput devices 704 include keyboards, keypads, gesture or graphicalinput devices, motion input devices, touchscreen interfaces, one or moredisplays, audio units, voice recognition units, vibratory devices,computer mice, and any other suitable user interface.

The processor 702 and memory 706 can include nonvolatile memory forstoring computable-readable instructions, data, data structures, programmodules, code, microcode, and other software components for storing thecomputer-readable instructions in non-transitory computable-readablemediums in connection with the other hardware components for carryingout the methodologies described herein. Software components can includesource code, compiled code, interpreted code, executable code, staticcode, dynamic code, encrypted code, or any other suitable type of codeor computer instructions implemented using any suitable high-level,low-level, object-oriented, visual, compiled, or interpreted programminglanguage.

These and other embodiments of the systems and methods may be used aswould be recognized by those skilled in the art. The above descriptionsof various systems and methods are intended to illustrate specificexamples and describe certain ways of making and using the systemsdisclosed and described here. These descriptions are neither intended tobe nor should be taken as an exhaustive list of the possible ways inwhich these systems can be made and used. A number of modifications,including substitutions of systems between or among examples andvariations among combinations can be made. Those modifications andvariations should be apparent to those of ordinary skill in this areaafter having read this disclosure.

It is intended that the specification and examples be considered asexemplary only, with a true scope and spirit of the invention beingindicated by the following claims.

What is claimed is:
 1. A computer-implemented method of managing electronic payment transactions at a merchant location, the method comprising: initiating a check-out procedure for a consumer to complete a payment transaction at a point-of-sale (POS) terminal associated with a merchant; prompting the consumer to present a payment vehicle and interact with the POS terminal for completing the payment transaction; receiving an indication that a near field communication (NFC)-enabled payment vehicle interacted with the POS terminal; receiving customer data from the NFC-enabled payment vehicle; processing the payment transaction with the received customer data; receiving an indication that the NFC-enabled payment vehicle interacted a second time with the POS terminal; generating an e-receipt as a result of the second NFC interaction, the e-receipt comprising customizable features including consumer incentive features, interactive coupons, and/or loyalty rewards for the consumer; and transmitting the e-receipt to the NFC-enabled payment vehicle for display on the NFC-enabled payment vehicle.
 2. The method of claim 1, wherein transferring the e-receipt to the NFC-enabled payment vehicle comprises storing the e-receipt in a mobile wallet of the NFC-enabled payment vehicle; and wherein the displayed e-receipt comprises selection areas for the consumer to enable the customizable features.
 3. The method of claim 1, wherein the POS terminal is located at a brick-and-mortar retail location, wherein the POS terminal is configured to communicate with a point of interaction (POI) device, and wherein the POI device is one of a near field communication (NFC) device, a keypad, and a scanner.
 4. The method of claim 1, wherein prompting the consumer comprises: communicating via a display area of the POS terminal, and wherein prompting the consumer further comprises prompting the consumer to interact with the NFC device with an NFC-enabled payment vehicle.
 5. The method of claim 1, further comprising: if the POS terminal receives indication that the payment transaction is approved from the acquirer processor, then prompting the payment transaction result to the consumer.
 6. The method of claim 1, wherein prompting the payment transaction result to the consumer comprises signaling via the display area of the POS terminal and/or via a display area of the NFC-enabled payment vehicle; and further wherein prompting the payment transaction result to the consumer comprises prompting a second interaction between the NFC-enabled payment vehicle and the NFC reader to generate an electronic receipt (e-receipt) for finalizing the payment transaction.
 7. The method of claim 1, further comprising: receiving an indication that a selection area has been activated for a customizable feature; and displaying the customizable feature associated with the selected selection area.
 8. A system for managing electronic payment transactions at a merchant location, the system comprising: a data storage device storing instructions for managing electronic payment transactions at a merchant location; and a processor configured to execute the instructions to perform a method including the steps of: initiating a check-out procedure for a consumer to complete a payment transaction at a point-of-sale (POS) terminal associated with a merchant; prompting the consumer to present a payment vehicle and interact with the POS terminal for completing the payment transaction; receiving an indication that a near field communication (NFC)-enabled payment vehicle interacted with the POS terminal; receiving customer data from the NFC-enabled payment vehicle; processing the payment transaction with the received customer data; receiving an indication that the NFC-enabled payment vehicle interacted a second time with the POS terminal; generating an e-receipt as a result of the second NFC interaction, the e-receipt comprising customizable features including consumer incentive features, interactive coupons, and/or loyalty rewards for the consumer; and transmitting the e-receipt to the NFC-enabled payment vehicle for display on the NFC-enabled payment vehicle.
 9. The system of claim 8, wherein transferring the e-receipt to the NFC-enabled payment vehicle comprises storing the e-receipt in a mobile wallet of the NFC-enabled payment vehicle; and wherein the displayed e-receipt comprises selection areas for the consumer to enable the customizable features.
 10. The system of claim 8, wherein the POS terminal is located at a brick-and-mortar retail location, wherein the POS terminal is configured to communicate with a point of interaction (POI) device, and wherein the POI device is one of a near field communication (NFC) device, a keypad, and a scanner.
 11. The system of claim 8, wherein prompting the consumer comprises: communicating via a display area of the POS terminal, and wherein prompting the consumer further comprises prompting the consumer to interact with the NFC device with an NFC-enabled payment vehicle.
 12. The system of claim 8, further comprising: if the POS terminal receives indication that the payment transaction is approved from the acquirer processor, then prompting the payment transaction result to the consumer.
 13. The system of claim 8, wherein prompting the payment transaction result to the consumer comprises signaling via the display area of the POS terminal and/or via a display area of the NFC-enabled payment vehicle; and further wherein prompting the payment transaction result to the consumer comprises prompting a second interaction between the NFC-enabled payment vehicle and the NFC reader to generate an electronic receipt (e-receipt) for finalizing the payment transaction.
 14. The system of claim 8, further comprising: receiving an indication that a selection area has been activated for a customizable feature; and displaying the customizable feature associated with the selected selection area.
 15. A non-transitory computer readable medium for use on at least one computer system containing computer-executable programming instructions for managing electronic payment transactions at a merchant location, the method comprising: initiating a check-out procedure for a consumer to complete a payment transaction at a point-of-sale (POS) terminal associated with a merchant; prompting the consumer to present a payment vehicle and interact with the POS terminal for completing the payment transaction; receiving an indication that a near field communication (NFC)-enabled payment vehicle interacted with the POS terminal; receiving customer data from the NFC-enabled payment vehicle; processing the payment transaction with the received customer data; receiving an indication that the NFC-enabled payment vehicle interacted a second time with the POS terminal; generating an e-receipt as a result of the second NFC interaction, the e-receipt comprising customizable features including consumer incentive features, interactive coupons, and/or loyalty rewards for the consumer; and transmitting the e-receipt to the NFC-enabled payment vehicle for display on the NFC-enabled payment vehicle.
 16. The non-transitory computer readable medium of claim 15, wherein transferring the e-receipt to the NFC-enabled payment vehicle comprises storing the e-receipt in a mobile wallet of the NFC-enabled payment vehicle; and wherein the displayed e-receipt comprises selection areas for the consumer to enable the customizable features.
 17. The non-transitory computer readable medium of claim 15, wherein the POS terminal is located at a brick-and-mortar retail location, wherein the POS terminal is configured to communicate with a point of interaction (POI) device, and wherein the POI device is one of a near field communication (NFC) device, a keypad, and a scanner.
 18. The non-transitory computer readable medium of claim 15, wherein prompting the consumer comprises: communicating via a display area of the POS terminal, and wherein prompting the consumer further comprises prompting the consumer to interact with the NFC device with an NFC-enabled payment vehicle.
 19. The non-transitory computer readable medium of claim 15, further comprising: if the POS terminal receives indication that the payment transaction is approved from the acquirer processor, then prompting the payment transaction result to the consumer.
 20. The non-transitory computer readable medium of claim 15, wherein prompting the payment transaction result to the consumer comprises signaling via the display area of the POS terminal and/or via a display area of the NFC-enabled payment vehicle; and further wherein prompting the payment transaction result to the consumer comprises prompting a second interaction between the NFC-enabled payment vehicle and the NFC reader to generate an electronic receipt (e-receipt) for finalizing the payment transaction. 